Jump to content

- Usage

- # Invision Power Services (IPS) Integration - 3.7 - Trouble Shooting

  Followers 0

  VBScript Lua

  The Invision Power Services (IPS) Integration extension writes meaningful trace information into the server trace file, according to the trace recommendation from this blog post:

  - Don't be shy, be chatty!

  So, to figure the exact reason for the problem you need to take a look into that file. The following link explains where to find it and how to filter its content down to the call in question and call routing output only:

  - How to filter SwyxWare traces for call routing output of single call

  Once you have opened and filtered the trace file you need to search for the first trace lines written by the GSE action. Just look for these lines:

  For VBScript based call routing:

      -------> IPS.Class_Initialize

  For Lua based call routing:

      -------> IPS:Create

  The following lines will contain information of all things happened, like setting the parameters and calling the IPS REST API to create the specific item.

  If at some point an error occurs, you will see an error message in the trace.

  If the REST API call fails, for example because you entered an invalid APIKey, you will see the following line:

      IPS web request failed! ({
          "errorCode": "3S290\/7",
          "errorMessage": "INVALID_API_KEY"
      })

  A list of all possible REST API errors/excaptions (and their meaning) can be taken from the IPS REST API documentation:

  - Create Topic (POST /forums/topic)
  - Create Post (POST /forums/posts)
  - Create Blog Comment (POST /blog/comments)
  - Create Download Comment (POST /downloads/comments)
  - Create Page Comment (POST /cms/comments/{database_id})
  - Create Message (POST /core/messages)

  In addition the the error message you will also find the original response code of the web request into the REST API. If everything went fine, the response code is 201, otherwise its any other number (most likely >= 400), e.g.

      nResponseCode = 401

  By taking the detailed error information from the server trace file you should be able to fix your problem.

  In case you can't get your problem fixed or have specific questions, please open your own topic in the project forum.

  By Tom Wellige

  - August 26, 2024
  Share
  Share
  Followers 0
  Previous Page 3.6 - Create Message

## Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.